fix(security-container-scan): pin anchore/sbom-action by SHA for GHE allowlist#52
Merged
Conversation
…allowlist Replace floating @v0 tag with the enterprise-allowlisted commit (e22c389, v0.24.0). Tag refs fail NVIDIA GHE workflow validation even when the resolved SHA is allowlisted, which breaks downstream repos such as infra-controller that consume this composite action.
abegnoche
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
anchore/sbom-actiontoe22c389904149dbc22b58101806040fa8d37a610(v0.24.0) instead of floating@v0uses:ref against the enterprise allowlist;@v0fails instantly even when the resolved SHA is allowlisted (NVBug 6457170)NVIDIA/infra-controller) that consumesecurity-container-scan@<sha>Test plan
NVIDIA/dsx-github-actions/.github/actions/security-container-scan@...in infra-controllernot allowedon sbom-action)Follow-up (separate PRs)
docker-build/action.ymlstill uses@v3/@v5docker actions (may be covered by allowlist wildcards)helm-*actions usedcarbone/install-*@v1.xtags — audit if those hit the same issue